Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

implementations: add V2/V3 support and last updated #126

Merged
merged 1 commit into from
Nov 29, 2024
Merged

implementations: add V2/V3 support and last updated #126

merged 1 commit into from
Nov 29, 2024

Conversation

LDeakin
Copy link
Contributor

@LDeakin LDeakin commented Nov 29, 2024

The current implementations table does not indicate the state of the implementations. Hopefully, this gives some indication without much maintenance burden. I've made some guesses about the Zarr V2/V3 support for each implementation.

### Changes
- implementations:
  - transpose the table
  - add latest release/commit column
  - add Zarr V2/V3 support column
  - match capitalisation of implementation names to the author's intention
  - add implementations:
    - zarr-java (Java)
    - zarr3 (Rust)
    - charizarr (Rust)

I've also added some additional implementations. But they may not be worth including, given their maturity.

Partially addresses zarr-developers/zarr_implementations#66

@LDeakin
implementations: add V2/V3 support and last updated
de56f4b 
- adds implementations: zarr-java (Java), zarr3 (Rust), charizarr (Rust)
@joshmoore
Copy link
Member

Nice! 😍 I'm inclined to get this in ASAP and then we work to improve it. (I imagine we could just add a friendly button -- "See something out of date? Click here to request a change")

Another additional complexity I could see trying to get across are the implementations which only implemented the intermediate version of v3 in case someone searches for "v3" in their code base.

@joshmoore
Copy link
Member

One additional thought: I've not worked with these (very nice) URLs before:

https://img.shields.io/github/last-commit/freeman-lab/zarr-js
https://img.shields.io/github/release-date-pre/Unidata/netcdf-java

etc. I assume it's a manual choice which one to use?

@joshmoore
Copy link
Member

see https://zarr-developersgithubio--126.org.readthedocs.build/en/126/implementations/ for the rendered page
image

@joshmoore joshmoore merged commit a20a850 into zarr-developers:main Nov 29, 2024
1 check passed
@LDeakin
Copy link
Contributor Author

LDeakin commented Nov 29, 2024

One additional thought: I've not worked with these (very nice) URLs before:

https://img.shields.io/github/last-commit/freeman-lab/zarr-js https://img.shields.io/github/release-date-pre/Unidata/netcdf-java

etc. I assume it's a manual choice which one to use?

Yeah, it was manual. I chose the first option if the repo was not using GitHub releases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@LDeakin @joshmoore